Methods and systems for imaging device remote application interaction

ABSTRACT

Aspects of the present invention relate to systems, methods and devices for interacting with a remote computing device from an imaging device. These aspects may comprise remote computing devices configured to communicate with imaging devices, imaging devices configured to communicate with remote computing devices and systems comprising various combinations of remote computing devices in communication with imaging devices.

BACKGROUND OF THE INVENTION

Imaging devices such as printers, copiers, scanners and fax machines canhave a wide array of functions and capabilities to fit specific uses orcombinations of uses. Imaging devices often take the form of amulti-function peripheral device (MFP) that combines the functions oftwo or more of the traditionally separated imaging devices. An MFP maycombine any number of imaging devices, but typically comprises thefunctions of a printer, scanner, copier and fax machine.

Some imaging devices may contain computing resources for data storageand processing such as processors, hard disk drives, memory and otherdevices. As imaging devices add more features and functions, they becomemore costly and complex.

More complex imaging devices and MFPs may comprise network connectivityto provide communication with other computing devices, such as personalcomputers, other imaging devices, network servers and other apparatus.This connectivity allows the imaging device to utilize off-boardresources that are available on a connected network.

Imaging devices typically have a user input panel with an array ofbuttons, knobs and other user input devices. Some devices also have adisplay panel, which can be for display only or can be a touch paneldisplay that enables user input directly on the display.

Devices with touch panel displays or displays with buttons arranged incooperation with the display can display menu data that may be selectedby user input. This menu data is typically driven by an on-board servermodule within the imaging device.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention comprise systems, methods anddevices for interacting with a remote computing device from an imagingdevice. These embodiments comprise remote computing devices configuredto communicate with imaging devices, imaging devices configured tocommunicate with remote computing devices and systems comprising variouscombinations of remote computing devices in communication with imagingdevices.

The foregoing and other objectives, features, and advantages of theinvention will be more readily understood upon consideration of thefollowing detailed description of the invention taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a diagram of an embodiment of the present invention comprisingan imaging device in connection with a remote computing device;

FIG. 2 is an image of an exemplary user interface for an imaging device;

FIG. 3 shows an exemplary imaging device;

FIG. 4 is a chart depicting steps of an imaging device method;

FIG. 5 is a chart depicting steps of an imaging device method using amarkup language;

FIG. 6 shows an exemplary remote computing device embodiment;

FIG. 7 is a diagram showing components of an exemplary remote computingdevice;

FIG. 8 is a chart showing steps of a remote computing device method;

FIG. 9 is a chart showing steps of a remote computing device methodusing a markup language;

FIG. 10 is a diagram showing a system comprising multiple imagingdevices in connection with a remote computing device;

FIG. 11A is a chart showing steps of a method that may be employed bythe system depicted in FIG. 10;

FIG. 11B is a chart showing embodiments comprising multi-languagesupport; and

FIG. 12 is a chart showing embodiments comprising error detection anderror resolution.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the present invention will be best understood byreference to the drawings, wherein like parts are designated by likenumerals throughout. The figures listed above are expressly incorporatedas part of this detailed description.

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the figures herein,could be arranged and designed in a wide variety of differentconfigurations. Thus, the following more detailed description of theembodiments of the methods and systems of the present invention is notintended to limit the scope of the invention but it is merelyrepresentative of the presently preferred embodiments of the invention.

Elements of embodiments of the present invention may be embodied inhardware, firmware and/or software. While exemplary embodiments revealedherein may only describe one of these forms, it is to be understood thatone skilled in the art would be able to effectuate these elements in anyof these forms while resting within the scope of the present invention.

Embodiments of the present invention comprise interfaces andarchitecture that integrate imaging devices with remote computing deviceapplications and environments to provide solutions that may not bepossible solely with an imaging device alone. Some embodiments comprisean infrastructure and set of interfaces that allow applications on anetwork to programmatically control imaging device functions andinteract with a user through an imaging device input panel. Softwarefunctions that are not practical within the imaging device can beperformed on the server but are accessible from the imaging device.

For the purposes of this specification and claims, an imaging device(IDev) may be described as a device that performs an imaging function.Imaging functions comprise scanning, printing, copying, imagetransmission (sending and receiving), image conversion and otherfunctions. Exemplary imaging devices comprise printers, copiers,facsimile machines, scanners, computing devices that transmit, convertor process images and other devices. An IDev may also perform multipleimaging functions. For example, and not by way of limitation, amulti-function peripheral device (MFP), which typically has thecapability to perform a plurality of functions comprising a printer,scanner, copier and/or a facsimile machine or imagetransmitter/receiver, is a type of imaging device. Other MFP imagingdevices may comprise other combinations of functions and still qualifyas an IDev.

For the purposes of this specification and claims, a remote computingdevice (RCD) is a device capable of processing data and communicatingwith other devices through a communications link. An RCD is a remotedevice because it requires a communications link, such as a networkconnection, a telephone line, a serial cable or some other wired orwireless link to communicate with other devices such as an imagingdevice. Some exemplary RCDs are network servers, networked computers andother processing and storage devices that have communications links.

Some embodiments of the present invention may be described withreference to FIGS. 1 & 2. These embodiments comprise an imaging device(IDev) 4 that may be a multi-function peripheral device (MFP) or asingle function device. The imaging device 4 further comprises a userinterface (UI) panel 2, which may comprise input buttons 14 and adisplay device 12 or may comprise a touch panel system with or withoutbuttons 14. User input and display may also be performed through aseparate UI device 8, which may be connected to the imaging device 4 bya communication link 12, such as a USB connection, a network cable, awireless connection or some other communications link. UI device 8 maycomprise an input device, such as a keyboard or buttons as well as adisplay device, which may also be a touch screen panel. UI device 8 mayalso comprise an interface for transfer of instructions that are inputto the device 8 from a remote input device. This form of UI device 8 maycomprise memory sticks, USB memory cards and other storage devices thatmay be configured to store input for transfer to an imaging device.

These embodiments further comprise a remote computing device (RCD) 6that is linked to the imaging device 4 via a communications link 10,such as a network connection. This network connection may be a typicalwired connection or a wireless link.

Embodiments of the present invention may provide menu data from the RCD6 to the imaging device UI panel 2 or remote panel 8 via the networkconnection 10. Once this menu data is fed to the imaging device 4, an UIpanel 2, 8 on the imaging device 4 may be used to interact withapplications that run on the remote computing device 6. User inputreceived from UI panels 2, 8 may be returned directly to the remotecomputing device 6.

A Web Service is a software application identified by a Uniform ResourceIdentifier (URI), whose interfaces and binding are capable of beingdefined, described and discovered by Extensible Markup Language (XML)artifacts and supports direct interactions with other softwareapplications using XML based messages via Internet-based protocols.

An application on the remote computing device 6 may use one or more WebServices to control various features in the imaging device 4, such asenabling, disabling or setting device values or controlling devicefunctions.

Embodiments of the present invention allow network applications runningon remote computing devices to interact with the user of the imagingdevice through the imaging device I/O panel. These embodiments allowimaging device user interface (UI) control (i.e., touch panel,button/display) by applications. Some embodiments may also integratecustom display screens or menus with the native imaging device UI.Embodiments may hand off control of imaging device functions betweenstandard operation modes performed on the imaging device in response touser input to an imaging device UI and open systems modes that utilizenetwork resources, such as applications on RCDs, through user input atthe imaging device UI.

Embodiments of the present invention comprise network-based applicationsthat have full control over the imaging device UI to display text andgraphics in any format. In these embodiments, the application canprogrammatically display buttons, textboxes, graphics, etc. in anylayout desired.

In some embodiments, the UI layout is easy to program using a standardlanguage, such as a markup language. These languages comprise HypertextMarkup Language (HTML), Extensible Markup Language (XML), WirelessMarkup Language (WML), Extensible Hypertext Markup Language (XHTML) andother languages.

In some embodiments of the present invention a remote computing deviceapplication or server application is able to request a keyboard UI to bedisplayed on the imaging device display 12, 8. In some embodiments, thisfunctionality is available on the imaging device and does not need to berecreated by remote computing device applications. In some embodiments,the remote computing device may define the keyboard prompt and defaultvalues. These embodiments may comprise a remote computing device that isable to rename imaging device UI buttons, such as the OK and Cancelbuttons as well as define additional buttons.

In some embodiments, menu templates may be served to the imaging deviceUI by the imaging device itself 4 or from a remote computing device 6.

External Authorization Application

Some embodiments of the present invention may comprise a remotecomputing device application that is registered as the ExternalAuthorization server. The External Authorization application may controlaccess to the imaging device and may have top-level control of the UI.UI control may be given to this application in the same manner thatcontrol is given to an internal auditor.

In these embodiments, when an imaging device system boots, it checks tosee if an External Authorization application is registered. If so, theimaging device is placed in disabled mode and the application iscontacted to take control of the UI. If the External Authorizationserver is not available, an error message may be displayed and thedevice may remain disabled. The imaging device may periodically try tocontact the External Authorization server until it is available. Table 1below describes what entity has control of the UI, in an exemplaryembodiment, when the device is in a disabled state.

TABLE 1 UI Control in Disabled State Indicator Button Press UI ControlLights Device boots External Application None Document Filing ExternalApplication None Image Send External Application None Copy ExternalApplication None Job Status Device - standard Job Status screens JobStatus Custom Settings Device - standard Custom Settings N/A screens OSMode Not available when device is disabledRemote Computing Device Applications

In embodiments of the present invention, access to the custom UI panelsof imaging devices may vary from application to application. Somesolutions, such as Document Management integration, may wish to leveragethe native Image Send screens, but display some custom UI's to gatheradditional information about a scan job. Other solutions, like customprinting applications, may be accessed from a separate mode than thenative functions.

In order to accommodate the diversified needs of these solutionsapplications, embodiments may support multiple integration points for UIcontrol. These integration points are based on a user action (“trigger”)for which applications may register. In some embodiments, applicationsmay be registered with target devices so that the device knows that when“trigger A” occurs on the front panel to contact “remote computingdevice B” for instructions. In exemplary embodiments, applications maybe integrated with an imaging device at any of several “trigger” points.

Remote computing devices may be registered to a specific function andcontacted when that function's hardware key is pressed (e.g. Image Send)on the imaging device UI. Any UI information provided by the remotecomputing device may be displayed instead of the standard functionscreens native to the imaging device. This trigger may be used forapplications that wish to replace the existing functions with completelycustom UI's, such as an alternative scan solution or a specializeddisplay, such as a “Section 508” compatible screen or otherspecialized-need interface that may have large buttons or otheraccommodations.

In some embodiments, each function on the imaging device may have a menuon the touch screen that remote computing devices, such as servers, canregister. This enables solutions applications to provide custom contentand still use some of the standard functionality provided by the imagingdevice. When a button assigned to a custom application is selected, amenu will be displayed with the solutions registered to that function.Users may select the desired solution and the remote computing devicewill be contacted for instructions.

In some embodiments, a stand-alone RCD mode that provides remotecomputing device application access can be accessed from the job queueportion of the UI that is displayed on every screen. This trigger pointmay be used for applications that do not fit within one of the standarddevice functions, such as custom printing solutions on an imagingdevice. When the RCD menu is selected, a menu will be displayed with thesolutions applications registered to the generic RCD mode. Users willselect the desired solution and the remote computing device will becontacted for instructions.

Hardware Key Interaction

In some embodiments of the present invention, when an imaging device isenabled, additional hardware keys may be used to manage the device.Hardware key assignments for an exemplary embodiment are shown in table2.

TABLE 2 Exemplary Hardware Key Assignments Standard IDev Button PressMode RCD Mode Mode keys (Copy, Clear current job Clear current jobsettings, Doc Filing, settings, move move to target screen Image Send)and to target screen Custom Settings key Job Status key Move to Job Moveto Job Status, Status, maintain maintain current settings currentsettings & UI location & UI location Clear (C) Clears settings Sendsclear event to external application Clear All (CA) Clears settings,Cancels job and returns to cancels job, and default IDev screen returnsto de- (notification sent to ex- fault IDev screen ternal application)**When External Authorization is control- ling the UI, only notifi-cation is sent Start Initiates scan Initiates scan function functionNumber keys Input for copy Not used count or fax numbers * Logs user outLogs user out (disable (disable device device and contact External andcontact Ex- Authorization for screens) ternal Authori- zation forscreens)

In some embodiments, in addition to the * key for logout, a timeoutperiod may be implemented. Some embodiments also comprise an auto clearsetting that can be configured for a given period of time, such as 10 to240 seconds (or disabled). In these embodiments, when there is noactivity for the time configured in auto clear, the device mayautomatically return to disabled mode and attempt to contact a remotecomputing device to retake control of the UI.

Error & Jam Notifications

Depending on a particular solution, a remote computing deviceapplication may have full or only partial control of the imaging deviceUI and a particular imaging job. In some embodiments, partial controlmay include cases where a remote computing device is monitoring clicks,but native modes are responsible for the UI interaction and controllingthe job. Partial control may also include cases where the remotecomputing device application is integrated with a native mode (UItrigger=function custom menu). In these embodiments, the imaging devicemay handle all error and jam notifications with only a notification sentto the relevant remote computing device application.

For some embodiments, in cases where the remote computing deviceapplication has full control over the UI and the job, error and jamnotifications may be handled differently depending on the type of error.For recoverable errors, a notification may be sent to the remotecomputing device application and the application may be responsible fordisplaying messages and resolving the error. For non-recoverable errors,the imaging device and RCD mode may interact to gracefully handle theerror condition (e.g. provide user with instructions for clearing jam).

Control Handoffs

In some embodiments, at different points throughout an imaging job,several applications may need control over an imaging device including,but not limited to, an External Authorization application, a standardRCD application, an imaging device native mode and other applications.The following section describes, for an exemplary embodiment, thevarious steps in an exemplary job, the entities that may have controlduring each step, and what type of control may be allowed.

STEP 1: User provides credentials to access the device at the device UI.This step may be controlled by a remote computing device, such as anExternal Authorization application or by Internal Accounting (nativemode) in the imaging device itself. At the end of this step, the deviceis enabled. The External Authorization application may also specifydefault parameters or disable specific job parameters (e.g. default fileformat is PDF, but user may change; color mode is set to B/W and usermay not change).

STEP 2: User sets parameters for the job using one of the native imagingdevice modes or a standard RCD application. At the end of this step theuser makes an input to initiate the job. When the input is made, anoptional notification may be sent to the standard RCD application, whichcan then change job parameters if desired. An e-mail application is oneexample of an application that may request notification when the userinput is made. A user may use native Image Send screens or other inputto select scan options and choose e-mail recipients. A user may thenselect a custom application button and choose the scan-to-e-mail optionfrom the menu. The e-mail application may then display custom screensfor the user to set permissions for the file. Once a user places theoriginal document(s) on the scanner and initiates the process, thee-mail application may capture the destination parameters set by theuser and change the target destination to the e-mail application FTPserver. The e-mail application may then receive the file, apply theappropriate permissions, and send to the e-mail recipients selected bythe user. A remote computing device application may also want to retakecontrol of the UI at this point, if, as in some embodiments, theapplication generates thumbnails of the scanned images and displays themto the user for verification.

STEP 3: Once the job is initiated, the imaging device is responsible forscanning or RIPing the job and spooling it to the HDD. If the imagingdevice is configured to authorize jobs with an external authorizationapplication, it may send a click report to the application and wait forinstructions. The external authorization application may enable the jobfor sending/printing, cancel the job, or change job parameters (and thenenable). As an example, a rules-based printing application may wish tochange job parameters after it receives a click report. Some rules-basedprinting applications support rules-based printing and scanning that canlimit what each user is allowed to do based on the time of day, thedestination, or many other parameters. For example, only users in themarketing group may be able to scan high-quality color images. If a userfrom another group selects color and 600 dpi, a rules-based applicationmay change the parameters to color and 200 dpi. At the end of this stepthe job should either be authorized or canceled.

STEP 4: In some embodiments, this may be an optional step, where thestandard RCD application in step 2 may have specified the destination asa HDD for temporary storage. This step may also be used, in someembodiments, by a Java application running on the imaging device. Forexample, a government office may have a custom encryption applicationrunning on the device that takes the scanned document, encrypts it, andthen requests the imaging device to send it to the target destinationselected by the user in step 2. In some embodiments, it may bebeneficial to send a notification to the external authorizationapplication after this step—because the imaging device does not know howlong the file will be on the HDD or what the application is going to dowith it—and after the send/print step.

STEP 5: In the final step, the file is actually output. In typicalembodiments, the file is either sent over the network or printedlocally. At the end of this step, a notification that the job wassuccessfully completed should be sent to the external authorizationapplication and optionally, to the standard RCD application.

Device Control and Management API's

The API's may be used to allow a remote computing device application tocontrol access to an imaging device for vend applications and to managethe device from a remote location.

Device Control and Vend API

In some embodiments of the present invention, a Device Control and VendAPI allows applications to enable and disable access to the device andtrack click counts. The Device Control and Vend API may provide an RCDwith the following controls:

ENABLE/DISABLE DEVICE OF FUNCTION—this may allow an RCD to enable ordisable access to the device as a whole or by function to enforceindividual user privileges. In some exemplary embodiments, the functionslisted in Table 3 may be selectively enabled or disabled by anapplication.

TABLE 3 Device Functions Enable/Disable Description Copy Copy function(Copy button) Image Send Scan and fax function, plus send from DocFiling (Image Send button) Document Filing All access to Document Filingfunctions (Document Filing button) Print Network prints, pull print fromfront panel, and print from Document Filing (No button control)

REPORT CLICKS USED—at the end of a successful job, the clicks used maybe reported back to an RCD including:

TABLE 4 Job and Page Characteristics Fax PC- E-mail/ Broad- Scan ItemCopy Print Send Fax FTP cast to HD JOB Characteristics Job Mode Yes YesYes Yes Yes Yes Yes Broadcast No No Yes Yes Yes Yes No Manage No. UserName Yes Yes Yes Yes Yes Yes Yes Address No No Yes Yes Yes # No StartTime Yes Yes Yes Yes Yes Yes Yes End Time Yes Yes Yes Yes Yes Yes YesTotal Page Yes Yes Yes Yes Yes Yes Yes Result Yes Yes Yes Yes Yes YesYes Error Cause No No Yes Yes Yes Yes No Doc Filing Yes Yes Yes Yes YesYes Yes Save Mode *1 *1 *1 *1 *1 *1 *1 File Name *1 Yes *1 Yes Yes *1Yes File Size Yes Yes *1 *1 *1 *1 Yes Resolution Yes Yes Yes Yes Yes YesYes Special Yes Yes Yes No Yes Yes Yes Finishing Yes Yes No No No No NoFile Format No No No No Yes Yes No Compression No No No No Yes Yes NoPAGE Characteristics Copy Yes Yes Yes Yes Yes # Yes Paper Size Yes YesYes Yes Yes Yes Yes Simplex/duplex Yes Yes Yes Yes Yes Yes Yes PaperType Yes Yes Yes Yes No No Yes Page Yes Yes Yes Yes Yes Yes Yes *1 - Yeswhen Document Filing is used

DEBIT MODE—in these embodiments, when an application enables the deviceit may specify if the current job requires authorization. If so, the jobwill be spooled to memory and click information (e.g., as defined inTable 4) will be sent to an RCD. An RCD will then notify the device ifthe job should be deleted or output/sent. At this point, the applicationalso has the option of changing job parameters. If the application doesnot require authorization, the job will continue as normal and a clickreport will be sent at the end of the job.

PRINT JOB ACCOUNTING—in these embodiments, an RCD may wish to monitorprint jobs along with walk-up functions. For print job accounting, anIDev may monitor all incoming print jobs and send accounting data in thePJL header to an RCD for verification before printing the job. The RCDwill evaluate the accounting data (or lack thereof) and inform the IDevto continue with or cancel the job.

REPORT ON UNIDENTIFIED JOBS—in these embodiments, an RCD may also wishto monitor print jobs that it cannot associate to a specific user, suchas device reports and incoming fax jobs. The RCD can register to receiveclick counts for all unidentified jobs, so that it may bill them to ageneral account.

Device Management API

In some embodiments of the present invention, a Device Management APIallows a network application to remotely setup and manage the imagingdevice. In exemplary embodiments, the Device Management API may providean RCD with the following controls:

-   -   DEVICE STATUS—an RCD may request the current status of the        device. This is the same status information as reported on the        embedded web pages.    -   DEVICE CONFIGURATION—an RCD can retrieve a list of installed        options supported by the device.    -   WEB PAGE SETTINGS—an RCD application can retrieve and set any of        the values that are configurable on the embedded web pages.    -   KEY OPERATOR PROGRAMS—an RCD application can retrieve and set        any of the values that are configurable in Key Operator        Programs, including software keys.    -   CUSTOM SETTINGS—an RCD application can retrieve and set any of        the values that are configurable in Custom Settings.    -   JOB STATUS—an RCD application can retrieve the current job queue        and history information and reprioritize or delete jobs in the        queue.    -   CLICK COUNTS—an RCD application can retrieve device total counts        and clicks for each function by account code.    -   DATA SECURITY SETTINGS—an RCD application may retrieve the        status information on the DSK (e.g. last erase) and initiate        data clear functions.    -   RED DATA—an RCD can retrieve all data typically sent in a RED        message.    -   REMOTE REBOOT—an RCD can initiate a reboot of the imaging        device.

The above groupings are provided only as an exemplary embodimentdetailing which settings should be included. In some embodiments, actualAPI's should be grouped by functional areas since there may be overlapbetween Key Operator settings and web page settings.

Internal Accounting API

In some embodiments, an Internal Accounting API may allow a remotecomputing device application to configure internal accounting and reportclick counts. In some exemplary embodiments an Internal Accounting APImay include:

-   -   SET AUDITING OPTIONS—an RCD may set auditing options including        which modes auditing is enabled for, “account number security”,        and “cancel jobs of invalid accounts.”    -   MANAGE ACCOUNT CODES—an RCD can add, edit, or delete account        codes    -   ACCOUNT LIMITS—an RCD application can specify a maximum number        of clicks by function for individual account codes or for all        account codes    -   ACCOUNT RESET—an RCD application can reset the click count for        an individual account or for all accounts    -   RETRIEVE CLICKS—an RCD can retrieve the number of clicks by        function for each account code        Font and Form Management API

Some embodiments of the present invention may comprise a Font and FormManagement API, which allows an RCD application to remotely download andmanage fonts and forms in mass-storage. In some exemplary embodiments, aFont and Form Management API may provide a remote computing device withthe following controls:

-   -   MASS STORAGE CONTROL—an RCD application can retrieve mass        storage status information including storage capacity, space        available, and write-protect mode plus modify write-protect        status.    -   RESOURCE LIST—an RCD application can retrieve a list of stored        fonts and forms including font or macro ID, font number,        font/form name, escape sequence, and file size.    -   DOWNLOAD RESOURCE—an RCD application can download PCL fonts, PCL        macros, and PS fonts and forms. Any special processing that is        performed when a resource is downloaded via the web pages will        also be performed when the resource is downloaded via Open        Systems.    -   DELETE RESOURCE—an RCD application can delete any resource        stored in mass storage.    -   UPLOAD RESOURCES—an RCD application can upload an individual or        all resources. On devices where effective memory management is        unavailable, a server application can use this function to        “defrag” mass storage.    -   FONT/MACRO ID's—an RCD application can assign or modify the ID's        assigned to PCL fonts and macros.        Firmware Management API

In some embodiments of the present invention, a Firmware Management APImay allow a remote computing device or network application to remotelydownload and manage the imaging device firmware. In some exemplaryembodiments, a Firmware Management API may provide a remote computingdevice (e.g., a server) with the following controls:

-   -   FIRMWARE VERSIONS—an RCD application can retrieve the current        firmware version numbers.    -   SERVICE MODE—an RCD application can place the MFP in service        mode to lockout other jobs that will interfere with firmware        upgrade. Upon receiving a service mode request, the IDev will        stop accepting incoming jobs, complete all jobs in the queue,        and then notify the server that it is in service mode.    -   UPDATE FIRMWARE—an RCD can download an updated firmware version        to the device. If a reboot is necessary, the IDev will perform        it automatically when download is complete.    -   DOWNLOAD STATUS—the IDev will send a status notification        (success/error) to an RCD after firmware download.    -   REVERT TO PREVIOUS VERSION—if firmware update is not successful,        the application can request the IDev to revert to the previous        firmware version.

Device Function API's

In some embodiments of the present invention, device function API'sallow a remote computing device application to use existing imagingdevice functionality to provide new custom solutions.

Image Send API

In some embodiments, an Image Send API may provide the remote computingdevice application with the following controls:

-   -   IMAGE SEND PARAMETERS—a remote computing device application can        get and set values for the following scan and fax parameters:        -   COLOR OR B/W        -   IMAGE MODE—TEXT, TEXT/PHOTO, PHOTO; EXPOSURE LEVEL        -   RESOLUTION        -   FILE FORMAT—FILE TYPE, COMPRESSION, AND PAGES PER FILE        -   ORIGINAL—ORIGINAL SIZE, SIMPLEX/DUPLEX, ROTATE, AND JOB            BUILD        -   FILENAME        -   SUBJECT        -   MESSAGE        -   SENDER        -   SCHEDULE SEND TIME        -   PAGE DIVISION (BOOK SCANNING)        -   COVER PAGE        -   TRANSMISSION MESSAGE (CONFIDENTIAL, URGENT, ETC.)        -   THIN PAPER SCANNING        -   DESTINATION        -   DOCUMENT FILING    -   INITIATE SCAN—the remote computing device application can        initiate the scan function (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if scanparameters may be modified by the user or not. If one remote computingdevice application (e.g. Access Control) specifies that a parametercannot be changed and then a second application (e.g. DocumentManagement) tries to set the parameter, a notification may be sent tothe second application and the setting will not be changed.

Print API

In some embodiments, print jobs may be submitted by remote computingdevice applications using standard printing channels. In some exemplaryembodiments, a Print API may provide a remote computing device with thefollowing additional control:

-   -   PJL SNIFFING—an RCD application can register with the IDev to be        contacted for instructions when a specific PJL command is found        in a print job. The RCD can then instruct the IDev to replace        the command, cancel the job, or continue printing. This        interface may be used in applications like accounting and        other-brand compatibility.        Copy API

In some embodiments of the present invention, a Copy API may provide aremote computing device with the following exemplary controls:

-   -   COPY PARAMETERS—an RCD application can get and set values for        the following copy parameters:        -   COLOR OR B/W        -   EXPOSURE—TEXT, TEXT/PHOTO, PHOTO, SUPER PHOTO; EXPOSURE            LEVEL        -   PAPER SELECT (BY TRAY)        -   COPY RATIO        -   2-SIDED COPY—1TO1, 1TO2, 2TO2, 2TO1; BINDING EDGE        -   OUTPUT—OUTPUT TRAY, SORT, STAPLE, GROUP, OFFSET        -   ORIGINAL SIZE        -   SPECIAL FUNCTIONS—MARGIN SHIFT, ERASE, PAMPHLET, ETC.        -   DOCUMENT FILING    -   INITIATE COPY—an RCD application can initiate the copy function        (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if copyparameters may be modified by the user or not.

Document Filing API

In some embodiments of the present invention, a Document Filing API mayprovide a remote computing device with the following exemplary controls:

-   -   BACKUP/RESTORE—the remote computing device application can        import and export a batch file with all Document Filing data. In        some embodiments, this package will be in a proprietary format        since it contains documents that are password-protected and        should not be accessed individually—this is typically for        restore in case of failure or cloning to other devices.    -   FILE/FOLDER LIST—the remote computing device application can        retrieve, modify, and create new files and folders to be stored        on the IDev (also covered in device management).    -   DOWNLOAD FILE—the remote computing device can download a new        file to the Document Filing systems and specify folder,        filename, username, and password.    -   USER LIST—the remote computing device application can retrieve,        modify, and create new users to be stored on the IDev (also        covered in device management).    -   HDD STATUS—the remote computing device application can retrieve        the current HDD status including the % allocated to the main        folder, quick folder, and custom folders and the % remaining.    -   DOC FILING PARAMETERS—the remote computing device application        can get and set values for storing a file to Doc Filing        including:        -   EXPOSURE        -   RESOLUTION        -   ORIGINAL—SIZE, SIMPLEX/DUPLEX        -   FILE INFORMATION—USERNAME, FILENAME, FOLDER, CONFIDENTIAL,            PASSWORD        -   SPECIAL MODES—ERASE, DUAL PAGE COPY, 2IN1, JOB BUILD, CARD            SHOT    -   INITIATE PRINT—the remote computing device application can        select a stored file and initiate a print including the        following parameters:        -   PAPER SIZE/SOURCE        -   OUTPUT—SORT/GROUP, OUTPUT TRAY, STAPLE, PUNCH, OFFSET        -   SIMPLEX/DUPLEX (TABLET/BOOKLET)        -   TANDEM PRINT        -   NUMBER OF COPIES        -   DELETE OR STORE AFTER PRINTING    -   INITIATE SEND—the remote computing device application can select        a stored file and initiate a send including the following        parameters:        -   RESOLUTION        -   FILE FORMAT        -   DESTINATION        -   TIMER        -   SENDER        -   FILENAME        -   SUBJECT        -   MESSAGE

Security

Allowing external applications to control an imaging device opens up theimaging device to new security vulnerabilities. In embodiments of thepresent invention that provide some security measures, the followingexemplary items are security concerns that may be addressed by theremote computing device interface.

Access to remote computing device interfaces may be limited to validapplications. Embodiments provide extensive access and control of theimaging device, which poses a significant security risk. The interfaceof these embodiments may be protected from access by attackers, whilemaintaining ease of setup and use for valid solutions.

Confidential data (user credentials and job data) may be protectedduring network transfer. User credentials and job data may be securedduring network transfer to ensure that it cannot be stolen, an intrudercannot monitor device activity, and a man-in-the-middle attack cannotchange messages. Imaging devices may support Secure Sockets Layer (SSL)and other connections to ensure data is safe while being communicatedbetween the imaging device and remote computing device applications.

Administrators may have the ability to lock-down imaging device access.For users with strict security policies, administrators may have theability to disable access by remote computing devices or limit access tospecific applications. Administrators may have an option to register thelimited applications that they wish to access the imaging deviceinterfaces.

Remote computing device applications may ensure the imaging device isnot being “spoofed.” The remote computing device may be able toauthenticate an imaging device that it is contract with it to ensure anintruder cannot imitate the imaging device to collect networkconfiguration and password information, monitor file/folder structuresof a document management system, or spoof security settings and DSKstatus of the imaging device.

A remote computing device may ensure that the server is not being“spoofed.” The imaging device must be able to authenticate all remotecomputing devices that it is in contact with to ensure that an intruderis not spoofing the remote computing device's IP address. By pretendingto be the remote computing device, an intruder could steal usercredentials, redirect scanned documents, change device settings orfirmware, or bring down the access control system (either to provideaccess to unauthorized users or initiate a denial of service attack forvalid users).

Access control/vend applications may not be compromised when a remotecomputing device is unavailable. When the remote computing device isunavailable, it may not be acceptable to provide open access to thedevice. If the remote computing device is unavailable at startup orbecomes unavailable at anytime (e.g. someone disconnects network cable),the imaging device may immediately be disabled and an error messagedisplayed.

An administrator may be able to adjust a security level based on companyand application requirements. Security requirements can have a largeimpact on the time it takes to develop a remote computing deviceapplication and the resources required to implement the solution. Usersusing some embodiments may range from a small business with one imagingdevice, no IT staff, and a simple scan or print application to a largegovernment office using access control and audit trails to track alldevice activity. The security measures used to protect imaging deviceinterfaces may be adjustable by the administrator to match the targetenvironment.

The imaging device and remote computing device applications may be ableto hand-off user credentials. Users may be prompted to login at multiplepoints throughout a job. For example, an access control application oraccounting application may control total device access, the imagingdevice may have user authentication enabled for Image Send, and adocument management application may require user login before showing afolder list. In many environments, all of these applications will use acommon user database. In some embodiments, it is, therefore, desirablefor the applications to pass user credentials to each other, so thateach one does not have to repeat the authentication process.

Some embodiments of the present invention may be described withreference to FIG. 3. These embodiments comprise an imaging device only,which is configured to interact with a remote computing device, such asa server through a communications link. The imaging device 30 comprisesa user interface 32, which comprises a user input device 34, such as akeypad, one or more buttons, knobs or switches or a touch-screen paneland a display 36, which may comprise user input device 34 in the form ofa touch-screen panel.

Imaging device 30 will typically be capable of performing one or moreimaging functions including, but not limited to, scanning, printing,copying, facsimile transmission (sending and receiving) and others.

These embodiments further comprise a communications link 38, which maybe a wired connection (as shown in FIG. 3) comprising a network cable, aUniversal Serial Bus (USB) cable, a serial cable, a parallel cable, apowerline communication connection such as a HomePlug connection orother wired connections. Alternatively, the communications link 38 maycomprise a wireless connection, such as an IEEE 802.11(b) compliantconnection, a Bluetooth connection, an Infrared Data Association (IrDA)connection or some other wireless connection.

The operation of some imaging device embodiments may be explained withreference to FIG. 4. In these embodiments, menu data is received 40 froma remote computing device (not shown in FIG. 3), which is connected tothe imaging device 30 via the communication link 38 through a wired orwireless connection. This menu data is then displayed 42 on the imagingdevice user interface display 36. This display of remote menu data isintended to prompt a user to make an input on the user interface inputdevice 34.

Imaging devices of these embodiments are further configured to acceptinput from a user in response to a display of remote menu data andcommunicate 44 that user input to a remote computing device. In someembodiments, this user input data will be processed by a remotecomputing device. This may comprise running an application on the remotecomputing device. This processing may also comprise accessing andcommunicating data that is stored on the remote computing device.

The imaging devices of these embodiments are further configured toreceive 46 data resulting from processing the user input data. This maycomprise data generated by an application running on the remotecomputing device in response to the user input. The imaging device mayalso receive data that was stored on a remote computing device, such asa file server, in response to processing the user input.

Once the imaging device 30 has received 46 the processed data, theimaging device 30 may perform 48 a native function in response to thedata or using the data. For example, and not be way of limitation, theimaging device 30 may print a document that was stored on the remotecomputing device and modified on the remote computing device accordingto the user input. As another non-limiting example, the imaging device30 may active or enable functions (i.e., scanning, copying, printing,fax transmission) on the imaging device in response to the receipt 46 ofprocessed data.

Some, more specific, imaging device embodiments may be explained withreference to FIG. 5. In these embodiments, the imaging device 30 isconfigured to receive 50 menu data formatted in a markup language from aremote computing device. The communication link by which the menu datais communicated may be established and maintained using a HypertextTransfer Protocol (HTTP). The markup language may comprise terms fromHypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages.

Once the menu data is received 50, it may be displayed 52 on the imagingdevice user interface display 36. As in previously describedembodiments, the menu data is typically intended to prompt user input onimaging device user interface 32. Display 52 of the remotely-stored menudata may be accomplished with a browser application that is native tothe imaging device 30.

In these embodiments, the imaging device 30 is further configured toroute 54 user input received though its user interface 32 to a remotecomputing device. The remote computing device that receives the userinput may then run an application or otherwise process the user inputand return the results of the processing to the imaging device 30.Accordingly, the imaging device 30 is further configured to receive 56processed data from a remote computing device. In some embodiments, theimaging device 30 may perform one or more functions in response to thereceipt 56 of processed data.

Some embodiments of the present invention may be explained withreference to FIG. 6. These embodiment comprise a remote computing device(RCD) 60, which has a communications link 64. Communications link 64 maybe a wired connection (as shown in FIG. 6) comprising a network cable, aUniversal Serial Bus (USB) cable, a serial cable, a parallel cable, apowerline communication connection such as a HomePlug connection orother wired connections. Alternatively, the communications link 64 maycomprise a wireless connection, such as an IEEE 802.11(b) compliantconnection, a Bluetooth connection, an Infrared connection, such asthose defined in the Infrared Data Association (IrDA) standard or someother wireless connection. In some embodiments, RCD 60 may furthercomprise a data storage device 62, which is typically a hard drive, butmay also be an optical drive device, such as an array of compact diskdrives, flash memory or some other storage device.

Embodiments of RCD 60 may be further described with reference to FIG. 7.In these embodiments, RCD 60 comprises a processor 72 for processingdata and running programs such as operating systems and applications.RCD 60 may further comprise memory 74, which may be in the form ofRandom Access Memory (RAM) and Read Only Memory (ROM). Generally, anyapplications processed by processor 72 will be loaded into memory 74.RCD 60 may further comprise a network interface 78, which allows RCD 60to communicate with other devices, such as an imaging device 30. In someembodiments, RCD 60 may also comprise a user interface 80, but this isnot required in many embodiments. Storage 62 may be used to storeapplications and data that may be accessed by an imaging device 30 ofembodiments of the present invention. Processor 72, memory 74, storage62, network interface 78 and, optionally, user interface 80 aretypically linked by a system bus 76 to enable data transfer between eachcomponent. Communications link 64 may couple the RCD 60 to other devicesvia network interface 78.

In some embodiments, described with reference to FIG. 8, an RCD 60 maycomprise menu data stored on storage device 62 or in memory 74. Thismenu data may be configured for display on an imaging device userinterface 32. Menu data may be stored in many formats andconfigurations. In some embodiments menu data may take the form of termsexpressed with a markup language. The markup language may comprise termsfrom Hypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages. In these embodiments, menu data may besent 82 through a communications link 64 to an imaging device 30.Accordingly, menu data configured for display on an imaging device isstored on RCD 60.

An RCD 60, of some embodiments, will be further configured to receive 84user input obtained through the user interface 32 of an imaging device30 and transferred to the RCD 60 over communications links 38 & 64. Oncethis input data is received at an RCD 60, the input data may beprocessed 86. This processing 86 may comprise conversion of the data toa new format, execution of commands contained within the data or someother process. Once the input data has been processed 86, the processedoutput may be sent 88 back to the imaging device 30 where the processedoutput may be used in an imaging device process or function.

In some embodiments, as described with reference to FIG. 9, an RCD 60may send 90 menu data configured for an imaging device display 36 usinga markup language. The markup language menu data is then received at theimaging device 30 and displayed to a user. Typically, this will promptthe user to enter an input on the imaging device user interface 32. Thisuser input will then be sent by the imaging device 30 to the RCD 60. TheRCD 60 will then receive 92 the input data prompted by the display ofthe menu data on the imaging device 30. Once received, the input datamay be processed 94 on the RCD 60. Processing may comprise theselection, recordation and/or modification of a form, document or otherdata stored on RCD 60, the authorization of a user identified by theuser input, the translation of a document input by the user, generationof a map or other directions related to user input or some other processor function.

Some embodiments of the present invention may be described withreference to FIGS. 10 & 11. These embodiments comprise at least one RCD60 and a plurality of imaging devices 30 a-30 d. In these embodiments,at least one of the imaging devices 30 a-30 d comprises a user interface32 with a display 36 and user input panel 34 that is integral with thedisplay (i.e., touch-screen) or a separate input unit. RCD 60 isconnected to imaging devices 30 a-30 d by a communications link andnetwork 100 to enable data transmission between RCD 60 and imagingdevices 30 a-30 d.

In these embodiments, menu data is stored on RCD 60 and sent 110 to atleast one of the imaging devices 30 a-30 d where the menu data isdisplayed on a user interface. Any of Imaging devices 30 a-30 d thatreceive the menu data are configured to accept 112 and transmit 114 userinput to an RCD 60. Once the user input data is received at the RCD, thedata may be processed 116 as discussed in previously describedembodiments. The result of processing 116 may then be sent 118 back toany combination of the imaging devices 30 a-30 d.

In these embodiments, a single RCD 60 may be used to provide processingpower, resources and functionality to a plurality of imaging devices 30a-30 d without reproducing these resources in each imaging device. Insome embodiments, data generated by input on one imaging device 30 a maybe directed to another imaging device 30 d for processed data output orfinal processing.

Some embodiments of the present invention may comprise multi-languagemenu support. Some of these embodiments, illustrated in FIG. 11B, allowfor an initial selection or identification 101 of a user-preferredlanguage. This selection may comprise user input to select a preferredlanguage. This step may also comprise an automatic identification of auser-preferred language which may be achieved by a user identificationprofile linked to a language, a language identification based on thetext of a scanned document, a code printed on a scanned document or someother identification scheme.

Once the language has been selected or otherwise identified, theselection/identification data is sent 102 to an RCD, where the selectionis used to identify language-specific menu data that is sent 103 to theimaging device for display 104. A user may then respond to theselected-language menu data with input 105, which may be used to invokenative imaging device functions or may be sent 106 to the RCD for anynecessary processing. An RCD may then process 107 the input data andsend 108 any process input to a destination, such as the imaging device,an e-mail address, a memory location or some other destination.

The operation of some imaging device embodiments may be explained withreference to FIG. 12. In these embodiments, menu data is received 110from a remote computing device (not shown in FIG. 3), which is connectedto the imaging device 30 via the communication link 38 through a wiredor wireless connection. This menu data is then displayed 112 on theimaging device user interface display 36. This display of remote menudata is intended to prompt a user to make an input on the user interfaceinput device 34. Imaging devices of these embodiments are furtherconfigured to accept input from a user in response to a display ofremote menu data and communicate 114 that user input to a remotecomputing device. In some embodiments, this user input data will beprocessed by a remote computing device. This may comprise running anapplication on the remote computing device. This processing may alsocomprise accessing and communicating data that is stored on the remotecomputing device. The imaging devices of these embodiments are furtherconfigured to receive 116 data resulting from processing the user inputdata. This may comprise data generated by an application running on theremote computing device in response to the user input. The imagingdevice may also receive data that was stored on a remote computingdevice, such as a file server, in response to processing the user input.Once the imaging device 30 has received 116 the processed data, theimaging device 30 may perform 118 a native function in response to thedata or using the data. For example, and not be way of limitation, theimaging device 30 may print a document that was stored on the remotecomputing device and modified on the remote computing device accordingto the user input. As another non-limiting example, the imaging device30 may activate or enable functions (i.e., scanning, copying, printing,fax transmission) on the imaging device in response to the receipt 116of processed data. During performance 118 of an imaging device functionan error may be detected 120. In response to this error detection, anerror message may be sent 122 to the remote computing device to notifyan application thereon of the error. The remote computing device maythen determine an error resolution routine to resolve the erroridentified in the error message and send 124 an error resolution messageto the imaging device to communicate the error resolution routine to theimaging device. The imaging device may then respond 126 to the errorresolution message by resolving the problem as directed by the errorresolution message.

The terms and expressions which have been employed in the forgoingspecification are used therein as terms of description and not oflimitation, and there is no intention in the use of such terms andexpressions of excluding equivalence of the features shown and describedor portions thereof, it being recognized that the scope of the inventionis defined and limited only by the claims which follow.

1. A method for error handling while executing a remote application froman imaging device (IDev), said method comprising: providing a userinterface on said imaging device, said user interface comprising adisplay device, said user interface further comprising an input device;linking said imaging device to a remote computing device (RCD), said RCDcomprising a remote application executing on said remote computingdevice; said RCD further comprising menu data; feeding said menu data tosaid (IDev) for display on said display device in a manner that enablesa user to interact with said remote application by user input on said(IDev), wherein said menu data comprises a prompt for user credentialsto be displayed on said display device; receiving a user credential froma user at said IDev, wherein said user credential defines individualuser privileges for each of a copy function, a scan function, a documentfiling function and a network print function and wherein said usercredential comprises a user identification profile linked to a userlanguage; sending said user credential to an external authorizationapplication; determining whether said RCD is available to said IDev;disabling said IDev if said user credential is not successfullyauthenticated and if said RCD is unavailable; enabling functions of saidIDev based on said user credential when said user credential issuccessfully authenticated and said RCD is available to said IDev;receiving user input defining an imaging job with job parameters;sending said job parameters to said RCD in a job notification; modifyingsaid job parameters at said RCD based on said user credential therebycreating modified job parameters; executing said IDev using saidmodified job parameters; detecting an error; determining whether saiderror is recoverable; when said error is recoverable, sending an errormessage to said remote application on said RCD for resolution by saidremote application, wherein said resolution by said remote applicationcomprises sending a resolution message to said imaging device; and whensaid error is not recoverable, determining a configured timeout period;prompting a user for error correction action at said imaging devicedisplay device, wherein said prompting is accomplished using said userlanguage; detecting whether said user error correction action occurs;and configuring said imaging device to a disabled mode if said usercorrection action does not occur before said timeout period expires. 2.A method as described in claim 1 wherein said feeding is at leastpartially achieved by transport of data commands with a markup language.3. A method as described in claim 1 wherein said feeding is at leastpartially achieved by transport of data commands with an object accessprotocol.
 4. A method as described in claim 1 wherein said feeding is atleast partially achieved by transport of data commands with a markuplanguage and an object access protocol.
 5. A method as described inclaim 1 wherein said feeding is at least partially achieved by transportof data commands with a markup language selected from the set consistingof HTML, XML, WML and XHTML.
 6. A method as described in claim 1 whereinsaid feeding is at least partially achieved by transport of datacommands with XML and SOAP.
 7. A method as described in claim 1 whereinsaid linking and said enabling is at least partially achieved byexposing imaging device function and data interfaces defined by a WebServices Definition Language (WSDL).
 8. A method as described in claim 1wherein said linking and said enabling is at least partially achieved byexposing imaging device function and data interfaces using a WebService.
 9. A method for providing error-handling functions on animaging device (IDev), said method comprising: providing a userinterface on an imaging device, said user interface comprising a displaydevice, said user interface further comprising an input device; linkingsaid imaging device to a remote computing device (RCD), said RCDcomprising at least one application executing on said remote computingdevice; said RCD further comprising menu data for said (IDev) displaydevice; transmitting said menu data to said (IDev) for display on saiddisplay device in a manner that enables a user to interact with said atleast one application by user input on said input device; enablingselective initiation of said application by user input on said (IDev);receiving a user credential from a user at said IDev, wherein said usercredential defines individual user privileges for each of a copyfunction, a scan function, a document filing function and a networkprint function and wherein said user credential comprises a useridentification profile linked to a user language; sending said usercredential to an external authorization application; determining whethersaid RCD is available to said IDev; disabling said IDev if said usercredential is not successfully authenticated and if said RCD isunavailable; enabling functions of said IDev based on said usercredential when said user credential is successfully authenticated andsaid RCD is available to said IDev; receiving user input defining animaging job with job parameters; sending said job parameters to said RCDin a job notification; modifying said job parameters at said RCD basedon said user credential thereby creating modified job parameters;executing a modified imaging job at said IDev using said modified jobparameters; detecting an error in the execution of said modified imagingjob; determining whether said error is recoverable; when said error isrecoverable, sending an error message to said application for resolutionby said application, wherein said resolution by said remote applicationcomprises sending a resolution message to said imaging device; and whensaid error is not recoverable, determining a configured timeout period;prompting a user for error correction action at said user interfacedisplay device, wherein said prompting is accomplished using said userlanguage; detecting whether said user error correction action occurs;and configuring said imaging device to a disabled mode if said usercorrection action does not occur before said timeout period expires. 10.A method as described in claim 9 wherein said linking, said transmittingand said enabling is at least partially achieved by transport of datacommands with a markup language and an object access protocol.
 11. Amethod as described in claim 9 wherein said linking, said transmittingand said enabling is at least partially achieved by transport of datacommands with XML and SOAP.
 12. A method as described in claim 9 whereinsaid linking, said transmitting and said enabling is at least partiallyachieved by exposing imaging device function and data interfaces definedby Web Services Definition Language (WSDL).
 13. An imaging systemcomprising: an imaging device (IDev), said (IDev) comprising, a userinterface on said imaging device, said user interface comprising adisplay, said user interface further comprising an input device; aremote computing device (RCD), said RCD comprising an applicationexecuting on said RCD, wherein said application comprises an errorresolution routine for receiving an error message from said imagingdevice, resolving an error identified in said error message and sendinga resolution message back to said (IDev); and a communication linkconnecting said (IDev) to said RCD; wherein said user interface on said(IDev) is connected to said RCD such that interaction with saidapplication on said (RCD) may be achieved by input to said input deviceon said (IDev); said IDev UI for receiving a user credential from a userat said IDev, wherein said user credential defines individual userprivileges for each of a copy function, a scan function, a documentfiling function and a network print function and wherein said usercredential comprises a user identification profile linked to a userlanguage; a credential sender for sending said user credential to anexternal authorization application; an availability determiner fordetermining whether said RCD is available to said IDev; a disabler fordisabling said IDev if said user credential is not successfullyauthenticated and if said RCD is unavailable; an enabler for enablingfunctions of said IDev based on said user credential when said usercredential is successfully authenticated and said RCD is available tosaid IDev; said IDev UI for receiving user input defining an imaging jobwith job parameters; a job parameter sender for sending said jobparameters to said RCD in a job notification; a modifier for modifyingsaid job parameters at said RCD based on said user credential therebycreating modified job parameters; said IDev for executing a modifiedimaging job at said IDev using said modified job parameters; an errordetector; an error characterizer, wherein said error characterizerdetermines whether an error is recoverable; and an error resolver,wherein said error resolver sends an error message to said remotecomputing device when a recoverable error is detected and said errorresolver sends a user message to said imaging device user interfacedisplay when a non-recoverable error is detected, wherein user messageis in said user language; a determiner for determining a configuredtimeout period; a detector for detecting whether said user errorcorrection action occurs; and a disabler for configuring said imagingdevice to a disabled mode if said user correction action does not occurbefore said timeout period expires.
 14. An imaging system comprising: animaging device (IDev), said (IDev) comprising, a user interface on said(IDev), said user interface comprising a display device, said userinterface further comprising an input device; a remote computing device(RCD), said RCD comprising an application that can be executed on saidRCD; said RCD further comprising menu data; said RCD further comprisingan error resolution routine for receiving an error message from saidimaging device, resolving an error identified in said error message andsending an error resolution message back to said imaging device; acommunication link connecting said (IDev)to said RCD; wherein said menudata is transmitted over said network to said (IDev)for display on saiddisplay device in a manner that enables a user to interact with saidapplication on said RCD by user input on said user interface: said IDevUI for receiving a user credential from a user at said IDev, whereinsaid user credential defines individual user privileges for each of acopy function, a scan function, a document filing function and a networkprint function and wherein said user credential comprises a useridentification profile linked to a user language; a credential senderfor sending said user credential to an external authorizationapplication; an availability determiner for determining whether said RCDis available to said IDev; a disabler for disabling said IDev if saiduser credential is not successfully authenticated and if said RCD isunavailable; an enabler for enabling functions of said IDev based onsaid user credential when said user credential is successfullyauthenticated and said RCD is available to said IDev; said IDev UI forreceiving user input defining an imaging job with job parameters; a jobparameter sender for sending said job parameters to said RCD in a jobnotification; a modifier for modifying said job parameters at said RCDbased on said user credential thereby creating modified job parameters;said IDev for executing a modified imaging job at said IDev using saidmodified job parameters; an error detector; an error characterizer,wherein said error characterizer determines whether an error isrecoverable; and an error resolver, wherein said error resolver sends anerror message to said remote computing device application when arecoverable error is detected and said error resolver sends a message tosaid imaging device user interface display when a non-recoverable erroris detected a determiner for determining a configured timeout period; adetector for detecting whether said user error correction action occurs;and said disabler for configuring said imaging device to a disabled modeif said user correction action does not occur before said timeout periodexpires.
 15. A computer-readable medium comprising instructions forcontrolling an application on a remote computing device (RCD) from auser input device on an imaging device (IDev), said instructionscomprising the acts of: providing a user interface on said (IDev), saiduser interface comprising a display device, said user interface furthercomprising an input device; linking said (IDev)to a RCD, said RCDcomprising an application that can be executed on said RCD; said RCDfurther comprising menu data; said RCD further comprising an errorresolution routine for receiving an error message from said imagingdevice, resolving an error identified in said error message and sendingan error resolution message back to said imaging device; receiving saidmenu data at said (IDev)for display on said display device in a mannerthat enables a user to interact with said application by user input onsaid imaging device; receiving a user credential from a user at saidIDev, wherein said user credential defines individual user privilegesfor each of a copy function, a scan function, a document filing functionand a network print function and wherein said user credential comprisesa user identification profile linked to a user language; sending saiduser credential to an external authorization application; determiningwhether said RCD is available to said IDev; disabling said IDev if saiduser credential is not successfully authenticated and if said RCD isunavailable; enabling functions of said IDev based on said usercredential when said user credential is successfully authenticated andsaid RCD is available to said IDev; receiving user input defining animaging job with job parameters; sending said job parameters to said RCDin a job notification; modifying said job parameters at said RCD basedon said user credential thereby creating modified job parameters;executing a modified imaging job at said IDev using said modified jobparameters; detecting an error; determining whether said error isrecoverable; when said error is recoverable, sending an error message tosaid application for resolution by said application; and when said erroris not recoverable, determining a configured timeout period; prompting auser for error correction action at said user interface display device,wherein said prompting is accomplished using said user language;detecting whether said user error correction action occurs; andconfiguring said imaging device to a disabled mode if said usercorrection action does not occur before said timeout period expires. 16.A method for allowing remote application access from an imaging device(IDev), said method comprising: providing a user interface on said(IDev), said user interface comprising a display device capable ofreceiving and displaying menu data received from a remote computingdevice (RCD), said user interface further comprising an input devicecapable of interacting with an application running on said RCD;providing a connection on said (IDev)to allow communication with saidRCD; receiving a user credential from a user at said IDev, wherein saiduser credential defines individual user privileges for each of a copyfunction, a scan function, a document filing function and a networkprint function and wherein said user credential comprises a useridentification profile linked to a user language; sending said usercredential to an external authorization application; determining whethersaid RCD is available to said IDev; disabling said IDev if said usercredential is not successfully authenticated and if said RCD isunavailable; enabling functions of said IDev based on said usercredential when said user credential is successfully authenticated andsaid RCD is available to said IDev; receiving user input defining animaging job with job parameters; sending said job parameters to said RCDin a job notification; receiving modified job parameters from said RCDwherein said modified job parameters are modified based on permissionsrelated to said user credential; executing said IDev using said modifiedjob parameters; detecting an error; determining whether said error isrecoverable; when said error is recoverable, sending an error message tosaid application for resolution by said application; when said error isnot recoverable, determining a configured timeout period; prompting auser for error correction action at said user interface display device,wherein said prompting is accomplished using said user language;detecting whether said user error correction action occurs; configuringsaid imaging device to a disabled mode if said user correction actiondoes not occur before said timeout period expires; and an error messagereceiver on said imaging device, said error message receiver forreceiving an error resolution message indicating an error resolutionprocedure for an error identified in said error message sent from saidimaging device.
 17. A method as described in claim 16 wherein saidinteracting is at least partially achieved by transport of data commandswith a markup language.
 18. A method as described in claim 16 whereinsaid interacting is at least partially achieved by transport of datacommands with an object access protocol.
 19. A method as described inclaim 16 wherein said interacting is at least partially achieved bytransport of data commands with a markup language and an object accessprotocol.